Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support add/delete User manager my sql #1120

Merged
merged 47 commits into from
Jun 8, 2020

Conversation

buhongw7583c
Copy link
Contributor

A new PR related with original one:
#1101

Closes #1101

What this PR does / why we need it:
All the PR description and comments could be found from #1101.
Due to some technical issue, the original PR could not display the correct changed files and have to reopen a new PR.

Special notes for your reviewer:
All the PR description and comments could be found from #1101.

How does this PR make you feel:
gif

If applicable:

  • this PR contains documentation
  • this PR contains tests

@buhongw7583c
Copy link
Contributor Author

buhongw7583c commented Jun 1, 2020

@melonrush13 Mel, I had some technical issue with the original PR that the changed files are wrong so have to open an exactly new one but this time with the correct changed files list.
Now the mysqluser will be deleted when the IP address has no access to server. As you suggested, let's do the same handling with the AzureSqlUser issue #1112.

PROJECT Show resolved Hide resolved
Copy link
Contributor

@melonrush13 melonrush13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was able to...

  • Create the user and delete the user successfully
  • Create/Delete with keyvault set from adminSecret/adminSecretKeyVault successfully
  • Create/Delete with keyVaultToStoreSecrets successfully

Quick fix, Hong: Please address PROJECT file for accidentantal double declaration. Thanks!

Also - as for the other PR, please add documentation to the following file for this new operator, but also feel free to address in another PR!

We will address the improper connected IP (for firewallrule) in this ticket here

Tagging @frodopwns @jananivMS for additional eyes/comments

@buhongw7583c
Copy link
Contributor Author

@melonrush13 @frodopwns Mel and Erin, I think I need at least one of you to approve the PR? Thanks so much.

PROJECT Show resolved Hide resolved
jananivMS and others added 3 commits June 6, 2020 21:51
Co-authored-by: Dave Fellows <dave.fellows@microsoft.com>
Co-authored-by: Dave Fellows <dave.fellows@microsoft.com>
Co-authored-by: Dave Fellows <dave.fellows@microsoft.com>
@jananivMS jananivMS self-requested a review June 7, 2020 03:58
jananivMS and others added 2 commits June 7, 2020 20:46
@jananivMS
Copy link
Contributor

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Contributor

@jananivMS jananivMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Tested functionality using Helm and works.

@jananivMS
Copy link
Contributor

/azp run

@buhongw7583c buhongw7583c merged commit 725dc08 into Azure:master Jun 8, 2020
@azure-pipelines
Copy link

Pipelines were unable to run due to time out waiting for the pull request to finish merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

As an operator, I can use the Service operator to manage the users within MySQL database
5 participants